Skip to content

Upgrade @elastic/elasticsearch to 9.3.2#254726

Merged
afharo merged 2 commits intoelastic:mainfrom
afharo:upgrade-es-9.3.2
Feb 25, 2026
Merged

Upgrade @elastic/elasticsearch to 9.3.2#254726
afharo merged 2 commits intoelastic:mainfrom
afharo:upgrade-es-9.3.2

Conversation

@afharo
Copy link
Copy Markdown
Member

@afharo afharo commented Feb 24, 2026

Summary

Upgrades the ES client to the latest release.

Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

  • Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
  • Documentation was added for features that require explanation or tutorials
  • Unit or functional tests were updated or added to match the most common scenarios
  • If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
  • This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The release_note:breaking label should be applied in these situations.
  • Flaky Test Runner was used on any tests changed
  • The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines
  • Review the backport guidelines and apply applicable backport:* labels.

@afharo afharo added backport:version Backport to applied version labels v9.4.0 v9.3.2 Team:Core Platform Core services: plugins, logging, config, saved objects, http, ES client, i18n, etc t// release_note:skip Skip the PR/issue when compiling release notes labels Feb 24, 2026
@afharo afharo marked this pull request as ready for review February 24, 2026 16:18
@elasticmachine
Copy link
Copy Markdown
Contributor

Pinging @elastic/kibana-core (Team:Core)

@afharo afharo self-assigned this Feb 24, 2026
@afharo afharo enabled auto-merge (squash) February 24, 2026 16:19
@elasticmachine
Copy link
Copy Markdown
Contributor

💛 Build succeeded, but was flaky

Failed CI Steps

Test Failures

  • [job] [logs] Jest Tests #7 / discover responsive sidebar search bar customization should not render CustomDataViewPicker
  • [job] [logs] Scout: [ platform / discover ] plugin / local-serverless-observability_complete - Metrics in Discover - Grid Navigation - should paginate through metrics

Metrics [docs]

✅ unchanged

History

cc @afharo

@afharo afharo requested a review from a team February 25, 2026 00:33
@afharo afharo merged commit 3f2bff9 into elastic:main Feb 25, 2026
15 checks passed
@afharo afharo deleted the upgrade-es-9.3.2 branch February 25, 2026 08:25
@kibanamachine
Copy link
Copy Markdown
Contributor

Starting backport for target branches: 9.3

https://github.com/elastic/kibana/actions/runs/22388496585

@kibanamachine
Copy link
Copy Markdown
Contributor

💔 All backports failed

Status Branch Result
9.3 Backport failed because of merge conflicts

You might need to backport the following PRs to 9.3:
- [Dashboards as code] Add conversion functions from/to API filters interface and stored filters (#242043)

Manual backport

To create the backport manually run:

node scripts/backport --pr 254726

Questions ?

Please refer to the Backport tool documentation

@afharo afharo added backport:skip This PR does not require backporting and removed backport:version Backport to applied version labels v9.3.2 labels Feb 25, 2026
@afharo
Copy link
Copy Markdown
Member Author

afharo commented Feb 25, 2026

Skipping backports because we didn't backport #253660 due to all the type changes.

qn895 pushed a commit to qn895/kibana that referenced this pull request Mar 11, 2026
## Summary

Upgrades the ES client to the latest release.


### Checklist

Check the PR satisfies following conditions. 

Reviewers should verify this PR satisfies this list as well.

- [x] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)
- [x]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [x] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [x] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [x] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [x] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
- [x] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:skip This PR does not require backporting release_note:skip Skip the PR/issue when compiling release notes Team:Core Platform Core services: plugins, logging, config, saved objects, http, ES client, i18n, etc t// v9.4.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants